home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
tex-k-archive.gz
/
tex-k-archive
/
000400_kb@cs.umb.edu_Wed Mar 16 00:43:47 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-11
|
1KB
Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA24930
(5.65c/IDA-1.4.4 for <tex-k-exp@cs.umb.edu>); Wed, 16 Mar 1994 05:43:49 -0500
Received: by terminus.cs.umb.edu id AA27000
(5.65c/IDA-1.4.4 for tex-k); Wed, 16 Mar 1994 05:43:47 -0500
Date: Wed, 16 Mar 1994 05:43:47 -0500
From: "K. Berry" <kb@cs.umb.edu>
Message-Id: <199403161043.AA27000@terminus.cs.umb.edu>
To: tim@maths.tcd.ie, tex-k@cs.umb.edu
Subject: Re: Kpathsearch -- database searching
but I'd like to suggest that Karl might use
the standard db/ndb libraries,
rather than using home-grown db utilities.
I considered doing this, but rejected it.
[n]dbm is unacceptable, since its binary files are byte-order dependent.
db doesn't have that problem, but its input files are not readily made
for this task. I'd have to write and distribute and maintain a special
script to generate them.
Also, then people wanting to use the ls-R would have to obtain, compile,
and install db. This is not a trivial task.
And they would have to generate the binary version of the db input file,
and keep that up-to-date with the original.
All of this seemed far too complicated for our needs. My home-grown db
``utilities'' is really nothing but one 150-odd line file (db.c),
including comments :-)